User interface for phone call routing among devices

ABSTRACT

A first electronic device receives a phone call that was routed to the first electronic device by a call-routing service. While receiving the call, the first electronic device receives a request to route the phone call to a second electronic device. In response to receiving the request to route the phone call to the second electronic device, in accordance with a determination that a first routing criteria have been met, the first electronic device sends a request to the call-routing service to route the phone call to the second electronic device instead of routing the phone call to the first electronic device. In accordance with a determination that a second routing criteria have been met, the first electronic device causes call data associated with the call to be routed through the first electronic device to the second electronic device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/952,736, titled “USER INTERFACE FOR PHONE CALL ROUTING AMONGDEVICES,” filed Apr. 13, 2018, which is a continuation of U.S. patentapplication Ser. No. 14/503,327, titled “USER INTERFACE FOR PHONE CALLROUTING AMONG DEVICES,” filed Sep. 30, 2014, which claims priority fromU.S. Provisional Patent Application Ser. No. 62/005,990, titled “USERINTERFACE FOR PHONE CALL ROUTING AMONG DEVICES,” filed May 30, 2014. Allof these applications are incorporated by reference herein in theirentirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to user interfaces for routingphone calls among electronic devices.

BACKGROUND OF THE DISCLOSURE

Electronic devices that provide communications capabilities (e.g.,voice, text, and/or video communications) come in various form factors(e.g., phone, tablet, laptop, desktop, etc.). However, transferring acall from a phone to a tablet, for example, may be impossible in manycases.

SUMMARY OF THE DISCLOSURE

Many electronic devices provide communications capabilities (e.g.,voice, text, and/or video communications). There is a need to provide afast, efficient, and intuitive way for users to route phone calls (andother communications) among electronic devices. In particular, acall-routing service may or may not be able to route a phone calldirectly to a second electronic device in response to a request from thefirst electronic device (e.g., routing-service routing). Instead, thefirst electronic device optionally routes the phone call through thefirst electronic device to the second electronic device (e.g.,through-device routing). The embodiments described herein provide anintuitive way for a first electronic device to cause a phone call to berouted from the first electronic device to a second electronic deviceusing routing-service routing if it is available, and falling back onthrough-device routing if routing-service routing is unavailable.Further, embodiments described herein provide an intuitive way for afirst electronic device to pull a phone call from the second electronicdevice to the first electronic device and/or to push a phone call fromthe first electronic device to the second electronic device.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs, the one or more programscomprising instructions, which when executed by a first electronicdevice, cause the first electronic device to perform a method. Themethod includes: generating for presentation on a display a userinterface including a user interface object indicating that a phone callhas been routed to a second electronic device; while the user interfaceis presented on the display, receiving a request to route the phone callto the first electronic device; in response to the request, requestingcall data associated with the phone call; and after requesting the calldata, presenting the phone call at the first electronic device.

In accordance with some embodiments, a method is performed at a firstelectronic device with one or more processors and memory. The methodincludes: generating for presentation on a display a user interfaceincluding a user interface object indicating that a phone call has beenrouted to a second electronic device; while the user interface ispresented on the display, receiving a request to route the phone call tothe first electronic device; in response to the request, requesting calldata associated with the phone call; and after requesting the call data,presenting the phone call at the first electronic device.

In accordance with some embodiments, a first electronic device comprisesa memory; a display; and a processor coupled to the display and thememory. The processor is configured to perform a method comprising:generating for presentation on the display a user interface including auser interface object indicating that a phone call has been routed to asecond electronic device; while the user interface is presented on thedisplay, receiving a request to route the phone call to the firstelectronic device; in response to the request, requesting call dataassociated with the phone call; and after requesting the call data,presenting the phone call at the first electronic device.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Detailed Description below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a multifunction device with atouch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a multifunction device having a touch screen inaccordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface on a device with atouch-sensitive surface that is separate from the display in accordancewith some embodiments.

FIGS. 5A-5F illustrate block diagrams of exemplary electronic devices incommunication according to some embodiments of the disclosure.

FIGS. 6A-6D illustrate exemplary user interfaces for causing a phonecall to be routed from a first electronic device to a second electronicdevice in accordance with some embodiments of the disclosure.

FIGS. 7A-7D are flow diagrams illustrating a method of causing a phonecall to be routed from a first electronic device to a second electronicdevice in accordance with some embodiments.

FIGS. 8A-8H illustrate exemplary user interfaces for pulling a phonecall from a second electronic device to a first electronic device inaccordance with some embodiments of the disclosure.

FIGS. 9A-9C are flow diagrams illustrating a method of pulling a phonecall from a second electronic device to a first electronic device inaccordance with some embodiments.

FIGS. 10A-10I illustrate exemplary user interfaces for pushing a phonecall from a first electronic device to a second electronic device inaccordance with some embodiments of the disclosure.

FIGS. 11A-11C are flow diagrams illustrating a method of pushing a phonecall from a first electronic device to a second electronic device inaccordance with some embodiments.

FIG. 12 shows a functional block diagram of an electronic deviceconfigured in accordance with the principles of the various describedembodiments, in accordance with some embodiments of the disclosure.

DETAILED DESCRIPTION

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Exemplary Devices

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conferencing module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XIVIPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions, data on stores and other points ofinterest at or near a particular location, and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, audio circuitry 110, speaker 111, RFcircuitry 108, text input module 134, e-mail client module 140, andbrowser module 147, online video module 155 includes instructions thatallow the user to access, browse, receive (e.g., by streaming and/ordownload), play back (e.g., on the touch screen or on an external,connected display via external port 124), send an e-mail with a link toa particular online video, and otherwise manage online videos in one ormore file formats, such as H.264. In some embodiments, instant messagingmodule 141, rather than e-mail client module 140, is used to send a linkto a particular online video. Additional description of the online videoapplication can be found in U.S. Provisional Patent Application No.60/936,562, “Portable Multifunction Device, Method, and Graphical UserInterface for Playing Online Videos,” filed Jun. 20, 2007, and U.S.patent application Ser. No. 11/968,067, “Portable Multifunction Device,Method, and Graphical User Interface for Playing Online Videos,” filedDec. 31, 2007, the contents of which are hereby incorporated byreference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIGS. 5A-5F illustrate block diagrams of exemplary electronic devices incommunication according to some embodiments of the disclosure. Firstelectronic device 500 and second electronic device 502 are optionallyany electronic device, such as multifunction devices 100 or 300, asillustrated in FIGS. 1A-B, 2, and 3. For example, the first and secondelectronic devices 500 and 502 are optionally phones, tablets, laptops,desktops, etc., and devices 500 and 502 are optionally different kindsof electronic devices (e.g., a phone and a tablet, a laptop and a phone,etc.). Further, although FIGS. 5A-5F illustrate only first and secondelectronic devices in communication, the methods and/or processesdescribed herein (e.g., method 700, 900, and/or 1100) are optionallyperformed at the first electronic device 500 (or other electronicdevices) to route phone calls among any number of electronic devices.

The first and second electronic devices 500 and 502 are optionally incommunication with a call-routing service 504. A call-routing service504 is a local exchange carrier, a mobile network operator (MNO), avoice over Internet Protocol (VoIP) provider, other phone carrier, etc.The call-routing service 504 sends call data associated with a phonecall to one or both of the first electronic device 500 (as illustratedin FIG. 5B) and the second electronic device 502 (as illustrated in FIG.5C).

In some embodiments, the first electronic device 500 optionally causesthe phone call to be routed to the second electronic device 502, eitherby routing-service routing or by through-device routing (illustrated inFIGS. 5D and 5E). According to routing-service routing, the first device500 optionally sends a request to the call-routing service 504 to routethe phone call directly to the second electronic device 502. Accordingto routing-service routing, the first electronic device 500 optionallyroutes the call data through the first electronic device 500 to thesecond electronic device 502, as illustrated in FIG. 5D. Althoughexamples described herein refer to routing a phone call through a firstelectronic device to a second electronic device, embodiments of thedisclosure are not so limited and also apply to routing a phone callthrough a second electronic device 502 to a first electronic device 500,as illustrated in FIG. 5E.

In some embodiments, the first electronic device 500 and the secondelectronic device 502 are optionally in communication with a devicecoordination server 506, as illustrated in FIG. 5F. The devicecoordination server 506 (e.g., a server at a carrier, phone serviceprovider, internet service provider, other service provider, etc.)optionally stores information regarding the first and second electronicdevices and other electronic devices. The device coordination server 506optionally sends the information to the electronic devices. For example,the device coordination server 506 optionally stores information thatthe phone call has been routed to the second electronic device 502 andsends the information to the first electronic device 500 so that thefirst electronic device can request that the call be routed to the firstelectronic device.

User Interfaces and Associated Processes Through-Device Routing andRouting-Service Routing

Many electronic devices provide communications capabilities (e.g.,voice, text, and/or video communications). There is a need to provide afast, efficient, and intuitive way for users to route phone calls (andother communications) among electronic devices. In particular, acall-routing service may or may not provide routing-service routing. Theembodiments described below provide an intuitive way for a firstelectronic device to cause a phone call to be routed from the firstelectronic device to a second electronic device using routing-servicerouting if it is available, and falling back on through-device routingif routing-service routing is unavailable. In some embodiments, thefirst electronic device causes the phone call to be routed from thefirst electronic device to the second electronic device usingthrough-device routing if available, and falling back on routing-servicerouting if routing-service routing is unavailable. In some embodiments,other criteria are used to determine the particular routing scheme touse.

FIGS. 6A-6D illustrate exemplary user interfaces for causing a phonecall to be routed from a first electronic device to a second electronicdevice in accordance with some embodiments of the disclosure. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes described below with referenceto FIGS. 7A-7D.

FIG. 6A illustrates exemplary user interfaces of a first electronicdevice 500 and a second electronic device 502. A phone call is presentedon the first electronic device 500, and the user interface of the firstelectronic device optionally includes a caller identification 602, acall time 604, and call controls (mute 606, keypad 608, speaker 610, addcall 612, contacts 614, and end call 616, among other possibilities).For example, presenting a phone call optionally includes playing audiodata from the phone call. The phone call is not presented on the secondelectronic device 502, and the user interface of the second electronicdevice optionally includes a home screen user interface (or any otheruser interface of the second electronic device that is not a phone calluser interface for presenting the phone call already presented on thefirst electronic device 500).

In some embodiments, the first electronic device 500 optionally receivesa request to route the phone call to the second electronic device 502,and the first electronic device causes the phone call to be routed tothe second electronic device, as illustrated in FIG. 6B. The phone callis presented on the second electronic device 502, and the user interfaceof the second electronic device optionally includes a calleridentification 618, a call time 620, and call controls (mute 622, keypad624, speaker 626, add call 628, contacts 630, and end call 632, amongother possibilities). The phone call is not presented on the firstelectronic device 500, and the user interface of the first electronicdevice optionally includes a home screen user interface (or any otheruser interface of the first electronic device that is not a phone calluser interface for presenting the phone call that has been routed to thesecond electronic device 502).

In some embodiments, after the phone call has been routed to the secondelectronic device 502, a user interface object 634 is optionallydisplayed in the user interface of the first electronic device 500, asillustrated in FIG. 6C. The user interface object 634 indicates that thephone call has been routed to the second electronic device 502. In someembodiments, the user interface object 634 further indicates that thephone call has been routed through the first electronic device 500(e.g., if the phone call was routed using through-device routing).

In some embodiments, the first electronic device 500 optionally receivesinput corresponding to selection of the user interface object 634, andin response to the input, the phone call is pulled back to the firstelectronic device 500, as illustrated in FIG. 6D.

FIGS. 7A-7D are flow diagrams illustrating a method of causing a phonecall to be routed from a first electronic device to a second electronicdevice in accordance with some embodiments. The method is optionallyperformed at an electronic device as described above with reference toFIGS. 1A-B and 2-5 (e.g., electronic device 100, 300, 500, or 502,etc.). Some operations in method 700 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, the method 700 provides ways of causing a phone callto be routed from a first electronic device to a second electronicdevice, using routing-service routing if available, or through-devicerouting as a fallback. The method reduces the cognitive burden on a userwhen interacting with a user interface on the device by providing anintuitive user interface for routing a phone call among electronicdevices, thereby creating a more efficient human-machine interface. Forbattery-operated electronic devices, increasing the efficiency of theuser's interaction with the user interfaces conserves power andincreases the time between battery charges.

In some embodiments, a first electronic device 500 with one or moreprocessors and memory receives (702), at the first electronic device, aphone call that was routed to the first electronic device by acall-routing service (e.g., a local exchange carrier associated with thephone call, a mobile network operator (MNO) associated with the phonecall, a voice over Internet Protocol (VoIP) provider associated with thephone call, other phone carrier, etc.). In some embodiments, the phonecall is optionally an audio-only call. In some embodiments, the phonecall is optionally a video call. The phone call is optionally presentedat the first electronic device, as illustrated in FIG. 6A.

While receiving the phone call, the first electronic device receives(706) a request to route the phone call to a second electronic device502. For example, the first electronic device optionally receives userinput on the first electronic device requesting to route the phone callto the second electronic device (push request received at the firstelectronic device), the first electronic device receives the requestfrom a different electronic device such as the second electronic device(pull request received from the second electronic device), etc. In someembodiments, both devices are associated with a same user account and/orare on a same local network. In some embodiments, the request to routethe phone call to the second electronic device is optionally received(708) from the second electronic device (and the request is sent inresponse to input on the second electronic device answering the phonecall). In some embodiments, the request to route the phone call to thesecond electronic device optionally corresponds (710) to user inputreceived at the first electronic device.

In response to receiving the request to route the phone call to thesecond electronic device (712), in accordance with a determination thata first routing criteria have been met (714), the first electronicdevice sends (720) a request to the call-routing service to route thephone call to the second electronic device instead of routing the phonecall to the first electronic device (e.g., routing-service routing). Insome embodiments, the first routing criteria optionally include (718) acriterion that is met when the call-routing service has enabled acarrier routing protocol (e.g., routing-service routing: if the carrierhas can directly route the phone call to the second electronic devicewithout going through the first electronic device). In some embodiments,the carrier routing protocol is optionally determined based oninformation stored on the first electronic device. In some embodiments,the carrier routing protocol is optionally determined based oncommunication with a remote device, such as a carrier server that sendsinformation associated with the carrier routing protocol to the firstelectronic device.

Further in response to receiving the request to route the phone call tothe second electronic device (712), in accordance with a determinationthat a second routing criteria have been met (716), the first electronicdevice causes (730) call data associated with the phone call to berouted through the first electronic device to the second electronicdevice. For example, the first electronic device optionally receivesaudio data associated with the phone call at the first electronic deviceand sends the received audio data to the second electronic device, etc.In some embodiments, the second routing criteria optionally include(728) a criterion that is met when the call-routing service has notenabled the carrier routing protocol.

In some embodiments, after the phone call has been routed to the secondelectronic device, the phone call is optionally presented at the secondelectronic device as illustrated in FIGS. 6B and 6C.

In some embodiments, before receiving the request to route the phonecall, the first electronic device optionally opens (704) a connectionassociated with the phone call. Further in accordance with thedetermination that the first routing criteria (e.g., routing-servicerouting) have been met (714), the first electronic device closes (722)the connection associated with the phone call. In some embodiments, theconnection associated with the phone call is closed in response toreceiving confirmation that the second electronic device has opened aconnection associated with the phone call (724).

In some embodiments, in accordance with the determination that thesecond routing criteria (e.g., through-device routing) have been met(716), the first electronic device maintains (736) the connectionassociated with the phone call for the duration of the phone call. Insome embodiments, the first electronic device optionally receives (742)a hang-up command from the second electronic device. For example, inFIG. 6B, the second electronic devices optionally receives user input onthe end call user interface object 632, and in response the secondelectronic device sends a hang-up command to the first electronicdevice. In response to receiving the hang-up command, the firstelectronic device optionally closes (744) the connection associated withthe phone call. In some embodiments, in accordance with thedetermination that the second routing criteria have been met, the firstelectronic device optionally causes (740) additional data to be routedto the second electronic device (e.g., voicemail, SMS, etc.).

In some embodiments, causing call data associated with the phone call tobe routed through the first electronic device to the second electronicdevice optionally includes receiving (732) the call data and sendingdifferent data to the second electronic device (e.g., audio dataextracted from the call data, audio data and metadata, etc.).

In some embodiments, causing call data associated with the phone call tobe routed through the first electronic device to the second electronicdevice optionally includes receiving (734) the call data and sending thecall data to the second electronic device without extracting audiocontent from the call data (e.g., the call data is relayed, unchanged tothe second electronic device).

In some embodiments, in accordance with the determination that thesecond routing criteria (e.g., through-device routing) have been met,the first electronic device displays (738) a user interface objectindicating the phone call is routed through the first electronic device(e.g., on a display such as displays 112, 340, and/or 450 in FIGS. 1A-Band 2-4). For example, the first electronic device optionally displays astatus bar a different size, different color, etc. In FIG. 6C, the firstelectronic device displays user interface object 634 indicating thephone call is routed through the first electronic device. In someembodiments, the first electronic device receives (746) input thatcorresponds to selection of the user interface object (e.g., detecting atap gesture on the user interface object 634). In response to receivingthe input, the first electronic device optionally causes (748) the calldata to no longer be routed to the second electronic device (and startplaying back the call audio on a speaker of the first electronic device,such as speaker 111 illustrated in FIG. 1A). For example, FIG. 6Dillustrates the phone call presented on the first electronic device andnot presented on the second electronic device.

In some embodiments, in accordance with the determination that the firstrouting criteria (e.g., routing-service routing) have been met, thefirst electronic device optionally displays (726) a user interfaceobject indicating the phone call has been routed to the secondelectronic device (e.g., on a display such as displays 112, 340, and/or450 in FIGS. 1-4). For example, the same status bar is optionallydisplayed to indicate an ongoing call whether routing-service routing isused or through-device routing is used, so as to harmonize the userinterface no matter which routing scheme is supported by the carrier.

In some embodiments, there are optionally differences in functionalitydepending on the routing scheme. For example, if through-device routingis used, the phone call optionally ends on the second electronic deviceif the first electronic device is turned off or loses signal during thephone call. If routing-service routing is used, the phone calloptionally continues on the second electronic device if the firstelectronic device is turned off or loses signal during the phone call.For another example, the first electronic device is optionally able tomake a second phone call after routing the first phone call usingrouting-service routing. If through-device routing is used, the firstelectronic device is optionally unable to make a second phone call untilthe first phone call ends.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described above with respect to FIGS. 1A and 3) orapplication specific chips.

The operations described above with reference to FIGS. 7A-7D are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, receiving operation 702, receiving operation 706, sendingoperation 720, and causing operation 730 are, optionally implemented byevent sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub-event, such as selection of an object on a user interface.When a respective predefined event or sub-event is detected, eventrecognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

It should be understood that the particular order in which theoperations in FIGS. 7A-7D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 900 and 1100) are also applicable in an analogous manner tomethod 700 described above with respect to FIGS. 7A-7D. For example, theuser interfaces, user interface objects, affordances, phone controls,phone calls, routing schemes, and electronic devices described abovewith reference to method 700 optionally have one or more of thecharacteristics of the user interfaces, user interface objects,affordances, phone controls, phone calls, routing schemes, andelectronic devices described herein with reference to other methodsdescribed herein (e.g., methods 900 and 1100). For brevity, thesedetails are not repeated here.

Pull to First Device from Second Device

Many electronic devices provide communications capabilities (e.g.,voice, text, and/or video communications). There is a need to provide afast, efficient, and intuitive way for users to route phone calls (andother communications) among electronic devices. In particular, theembodiments below provide an intuitive way for a first electronic deviceto pull a phone call from a second electronic device to a firstelectronic device.

FIGS. 8A-8H illustrate exemplary user interfaces for pulling a phonecall from a second electronic device to a first electronic device inaccordance with some embodiments of the disclosure. The user interfacesin these figures are used to illustrate processes described below,including the processes described below with reference to FIGS. 9A-9C.

FIG. 8A illustrates example user interfaces of a first electronic device500 and a second electronic device 502. A phone call is presented on thesecond electronic device 502, and the phone call is not presented on thefirst electronic device 500. The user interface of the first electronicdevice 500 incudes a user interface object 802 indicating the phone callhas been routed to the second electronic device 502. FIG. 8A illustratesthe user interface object 802 displayed on a home screen of the firstelectronic device 502. In FIG. 8B, a user interface object 804indicating the phone call has been routed to the second electronicdevice 502 is displayed on a lock screen of the first electronic device.In FIG. 8C, a user interface object 806 indicating the phone call hasbeen routed to the second electronic device 502 is displayed on anotifications user interface of the first electronic device. In FIG. 8D,a user interface object 808 indicating the phone call has been routed tothe second electronic device 502 is displayed is displayed in a phonecall user interface of the first electronic device.

In some embodiments, input is optionally received on any of the userinterface objects 802, 804, 806, and 808 to cause the phone call to berouted to the first electronic device 500 (e.g., the phone call may bepulled to the first electronic device). In response to the input, thephone call is optionally presented on the first electronic device 500,as illustrated in FIG. 8E.

As illustrated in FIG. 8F, after the phone call is routed to the firstelectronic device, the user interface of the first electronic device 500optionally includes an identifier 810 of the second electronic device502 (e.g., indicating that the call was pulled from the secondelectronic device). In some embodiments, the user interface alsooptionally includes an affordance 812 for transferring the phone callback to the second electronic device, as illustrated in FIG. 8G. Inresponse, to selection of the affordance 812, the phone call isoptionally routed back to the second electronic device, as illustratedin FIG. 8H.

FIGS. 9A-9C are flow diagrams illustrating a method of pulling a phonecall from a second electronic device to a first electronic device inaccordance with some embodiments. The method is optionally performed atan electronic device as described above with reference to FIGS. 1-5(e.g., electronic device 100, 300, 500, or 502, etc.). Some operationsin method 900 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 900 provides ways of pulling a phone callfrom a second electronic device to a first electronic device. The methodreduces the cognitive burden on a user when interacting with a userinterface on the device by providing an intuitive user interface forrouting a phone call among electronic devices, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, increasing the efficiency of the user's interaction with theuser interfaces conserves power and increases the time between batterycharges.

In some embodiments, a first electronic device 500 with one or moreprocessors and memory generates (906) for presentation on a display(e.g., a remote display device or a display that is integrated into theelectronic device, such as displays 112, 340, and/or 450 in FIGS. 1-4) auser interface including a user interface object indicating that a phonecall has been routed to a second electronic device (e.g., text, an icon,or a button indicating the phone call on the second electronic device).In some embodiments, the user interface object indicating that the phonecall has been routed to the second electronic device is optionallydisplayed (916) on a lock screen of the first electronic device. In someembodiments, the user interface object indicating that the phone callhas been routed to the second electronic device is optionally displayed(918) as a notification at the first electronic device. In someembodiments, the user interface object indicating that the phone callhas been routed to the second electronic device is optionally displayed(920) in a phone call user interface on the first electronic device. Forexample, the user interface optionally includes any of user interfaceobjects 802 (status bar), 804 (on a lock screen), 806 (notification), or808 (in a phone call user interface) illustrated in FIGS. 8A-8D, amongother possibilities.

While the user interface is presented on the display, the firstelectronic device receives (922) a request to route the phone call tothe first electronic device (e.g., receiving user input on the firstelectronic device requesting to route the phone call to the firstelectronic device, receiving the request from a different electronicdevice, etc.). For example, the first electronic device optionallyreceives input selecting any of user interface objects 802 (status bar),804 (on a lock screen), 806 (notification), or 808 (in a phone call userinterface) illustrated in FIGS. 8A-8D, among other possibilities.

In response to the request, the first electronic device requests (924)call data (e.g., from a carrier associated with the phone call, from thesecond electronic device, etc.) associated with the phone call.

After requesting the call data, the first electronic device presents(932) the phone call at the first electronic device (e.g., in responseto requesting the call data, the call is routed to the first electronicdevice and the first electronic device connects the phone call). Forexample, FIGS. 8E-8G illustrate the phone call presented in a userinterface of the first electronic device.

In some embodiments, after requesting the call data, the firstelectronic device optionally instructs (930) the second electronicdevice to stop playing audio associated with the phone call (e.g.,through a speaker or headset in communication with the second electronicdevice, such as speaker 111 illustrated in FIG. 1A).

In some embodiments, while the phone call is presented at the firstelectronic device (934), the phone call is optionally not presented(936) at the second electronic device (e.g., the first device and thesecond device are not devices that share a common phone line).

In some embodiments, requesting the call data optionally includescausing (926) the call data to be routed through the second electronicdevice to the first electronic device (e.g., using through-devicerouting, as described above). In some embodiments, requesting the calldata optionally includes sending (928) a request to a routing service toreroute the phone call from the second electronic device to the firstelectronic device (e.g., using routing-service routing, as describedabove).

In some embodiments, the first electronic device optionally receives(902), from the second electronic device, information that the phonecall has been routed to the second electronic device, and the userinterface is generated based on the information (908). In someembodiments, the information that the phone call has been routed to thesecond electronic device is received prior to displaying user interfaceobject indicating that a phone call has been routed to a secondelectronic device on the display. For example, user interface objects802, 804, 806, and 808 in FIGS. 8A-8D include an identifier (“Device 2”)of the second electronic device, and such an identifier is optionallygenerated based on information that the phone call has been routed tothe second electronic device.

In some embodiments, the first electronic device optionally receives(904), from a device coordination server 506 (e.g., a server at acarrier, phone service provider, internet service provider, otherservice provider, etc. that optionally stores information regardingfirst and second electronic devices and optionally sends the informationto other electronic devices) that is in communication with the firstelectronic device and the second electronic device, information that thephone call has been routed to the second electronic device, and the userinterface is generated based on the information (904). For example, userinterface objects 802, 804, 806, and 808 in FIGS. 8A-8D include anidentifier (“Device 2”) of the second electronic device, and such anidentifier is optionally generated based on information from the devicecoordination server.

In some embodiments, while the phone call is presented at the firstelectronic device (934), the first electronic device optionallygenerates (938) for presentation on the display an affordance fortransferring the phone call back to the second electronic device. Forexample, FIG. 8G illustrates an affordance 812 displayed on the firstelectronic device for transferring the phone call back to the secondelectronic device. In some embodiments, the first electronic deviceoptionally detects (942) selection of the affordance, and in response todetecting selection of the affordance, the first electronic devicecauses (944) the phone call to be routed back to the second electronicdevice (using the same approach that was used to pull the call from thesecond electronic device). For example, FIG. 8H illustrates the phonecall presented at the second electronic device after selection of theaffordance 812 in FIG. 8G.

In some embodiments, while the phone call is presented at the firstelectronic device (934), the first electronic device optionallygenerates (940) for presentation on the display an identifier of thesecond electronic device (e.g., text indicating that the call is routed“from your iPhone”, etc.). For example, FIGS. 8F and 8G illustrate anidentifier 810 (“pulled from Device 2”) of the second electronic device.

In some embodiments, the user interface object is optionally generated(910) in accordance with a determination that the first and secondelectronic devices are both associated with the same user identity. Insome embodiments, the user interface object is optionally generated(912) in accordance with a determination that the first and secondelectronic devices are connected to the same network (e.g., the sameWiFi, the same subnet, etc.). In some embodiments, the user interfaceobject is optionally generated (914) in accordance with a determinationthat the second electronic device is Bluetooth discoverable from thefirst electronic device. For example, the first electronic device isoptionally only able to pull phone calls from devices that areassociated with the same user identity, on the same network, and/orBluetooth discoverable from the first electronic device, among otherpossibilities (e.g., this allows routing only to devices that arecompatible with the routing scheme and provides an element of securityto the pushing/pulling/etc.).

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described above with respect to FIGS. 1A and 3) orapplication specific chips.

The operations described above with reference to FIGS. 9A-9C are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, generating operation 906, receiving operation 922, requestingoperation 924, and presenting operation 932 are, optionally implementedby event sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub-event, such as selection of an object on a user interface.When a respective predefined event or sub-event is detected, eventrecognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

It should be understood that the particular order in which theoperations in FIGS. 9A-9C have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 1100) are also applicable in an analogous manner tomethod 900 described above with respect to FIGS. 9A-9C. For example, theuser interfaces, user interface objects, affordances, phone controls,phone calls, routing schemes, and electronic devices described abovewith reference to method 900 optionally have one or more of thecharacteristics of the user interfaces, user interface objects,affordances, phone controls, phone calls, routing schemes, andelectronic devices described herein with reference to other methodsdescribed herein (e.g., methods 700 and 1100). For brevity, thesedetails are not repeated here.

Push from First Device to Second Device

Many electronic devices provide communications capabilities (e.g.,voice, text, and/or video communications). There is a need to provide afast, efficient, and intuitive way for users to route phone calls (andother communications) among electronic devices. In particular, theembodiments below provide an intuitive way for a first electronic deviceto push a phone call from a first electronic device to a secondelectronic device.

FIGS. 10A-10I illustrate exemplary user interfaces for pushing a phonecall from a first electronic device to a second electronic device inaccordance with some embodiments of the disclosure. The user interfacesin these figures are used to illustrate processes described below,including the processes described below with reference to FIGS. 11A-11C.

FIG. 10A illustrates example user interfaces of a first electronicdevice 500 and a second electronic device 502. A phone call is presentedon the first electronic device 500, and the phone call is not presentedon the second electronic device 502. The user interface of the firstelectronic device 500 includes an affordance 1002 associated with thesecond electronic device (e.g., the affordance includes text “Push toDevice 2”). FIG. 10A illustrates the affordance 1002 displayed in aphone call user interface of the first electronic device 500. In someembodiments, the second electronic device is optionally selected as adevice capable of receiving the phone call. In some embodiments, thesecond electronic device is optionally included in a plurality ofelectronic devices selected as devices capable of receiving the phonecall. FIG. 10B illustrates a plurality of affordances 1004, 1006, 1008,and 1010, each associated with an electronic device capable of receivingthe phone call. Further, FIG. 10C illustrates that the second electronicdevice is optionally selected as a device capable of receiving the phonecall even when the second electronic device is in an inactive state(e.g., locked, sleep mode, hibernate, powered off, etc.).

In some embodiments, input is optionally received on the affordance 1002to cause a phone call application to be invoked on the second electronicdevice to receive the phone call and call data is routed to the secondelectronic device, as illustrated in FIG. 10D. Further, FIG. 10Dillustrates that the phone call is no longer presented on the firstelectronic device.

In some embodiments, a phone call interface is displayed on the firstelectronic device 500 even though the phone call is no longer presentedon the first electronic device (e.g., audio of the phone call is notplayed on the first electronic device and/or call data associated withthe phone call is not received, among other possibilities), asillustrated in FIG. 10E. The phone call interface optionally includes acaller identification 1012, a call time 1014, and call controls (mute1016, keypad 1018, speaker 1020, add call 1022, contacts 1024, and endcall 1026, among other possibilities). The call controls are optionallyused to control the phone call on the second electronic device. Forexample, receiving user input on the end call control 1026 optionallycauses a hang-up command to be sent to the second electronic device,which causes the call to hang-up on the second electronic device.

In some embodiments, hanging up the phone call at the second electronicdevice optionally causes a hang-up notification to be received at thefirst electronic device as illustrated in FIGS. 10F and 10G. FIG. 10Fillustrates an end call control 1028 on the second electronic device.Receiving user input on the end call control 1028 optionally causes thesecond electronic device to hang-up the phone call, and the firstelectronic device optionally receives an indication that the secondelectronic device ended the phone call. In response to receiving theindication, the first electronic device optionally displays anotification 1030 that the second electronic device ended the call, asillustrated in FIG. 10G.

In some embodiments, after pushing the phone call to the secondelectronic device, the first electronic device optionally displays aphone call user interface including an affordance 1032 for causing thecall data to be routed back to the first electronic device, asillustrated in FIG. 10H. In response to detecting selection of theaffordance, the first electronic device optionally causes the phone callto be routed back to the first electronic device, as illustrated in FIG.10I.

FIGS. 11A-11C are flow diagrams illustrating a method of pushing a phonecall from a first electronic device to a second electronic device inaccordance with some embodiments. The method is optionally performed atan electronic device as described above with reference to FIGS. 1-5(e.g., electronic device 100, 300, 500, or 502, etc.). Some operationsin method 1100 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 1100 provides ways of pushing a phonecall from a first electronic device to a second electronic device. Themethod reduces the cognitive burden on a user when interacting with auser interface on the device by providing an intuitive user interfacefor routing a phone call among electronic devices, thereby creating amore efficient human-machine interface. For battery-operated electronicdevices, increasing the efficiency of the user's interaction with theuser interfaces conserves power and increases the time between batterycharges.

In some embodiments, while receiving a phone call on a first electronicdevice 500 with one or more processors and memory (1102), the firstelectronic device generates (1104) for presentation on a display (e.g.,a remote display device or a display that is integrated into theelectronic device, such as displays 112, 340, and/or 450 in FIGS. 1-4) auser interface including a first affordance associated with a secondelectronic device 502 capable of receiving the phone call (e.g., aphone, a tablet, a computer, etc.). For example, FIG. 10A illustrates auser interface including a first affordance 1002 associated with thesecond electronic device.

The first electronic device detects (1116) selection of the firstaffordance (e.g., touch input on the first affordance, a click, a keypress, etc.).

In response to detecting the selection of the first affordance (1118),the first electronic device instructs (1122) the second electronicdevice to invoke a phone call application to receive the phone call. Forexample, FIG. 10D illustrates the second electronic device displaying auser interface of a phone call application to receive the phone call. Insome embodiments, in response to detecting selection of the firstaffordance (1118), the first electronic device transmits (1120), to thesecond electronic device, a communication that causes the secondelectronic device to wake from an inactive state (and/or unlock from alocked state). FIG. 10C illustrates the second electronic device in aninactive state (prior to receiving a communication causing it to wakefrom the inactive state). The phone call application is optionallyinvoked after the second electronic device wakes from the inactivestate.

Further in response to detecting the selection of the first affordance(1118), the first electronic device causes (1124) call data associatedwith the phone call to be routed to the second electronic device (e.g.,by routing the call data through the first electronic device, byinstructing a carrier associated with the phone call to route the phonecall to the second electronic device, etc.).

In some embodiments, after causing the call data to be routed to thesecond electronic device, the first electronic device receives (1132)input controlling the phone call (e.g., mute the call, put the call onhold, hang-up the call, etc.). For example, the first electronic deviceoptionally receives input on phone call controls 1016-1026 illustratedin FIG. 10E. The first electronic device optionally controls the phonecall in accordance with the received input (e.g., by sending to thesecond electronic device a corresponding command to mute the call, putthe call on hold, hang-up the call, etc.).

In some embodiments, the first electronic device receives (1136) ahang-up command from the second electronic device. For example, ahang-up command is optionally sent by the second electronic device inresponse to input selecting the end call control 1028 illustrated inFIG. 10F. In response to receiving the hang-up command (1138), the firstelectronic device optionally closes (1140) a connection associated withthe phone call. In some embodiments, in response to receiving thehang-up command (1138), the first electronic device optionally causes(1142) the phone call to be routed back to the first electronic device(e.g., instead of closing the connection).

In some embodiments, the first electronic device optionally receives(1144) an indication that the second electronic device ended the phonecall. In response to receiving the indication that the second electronicdevice ended the phone call, the first electronic device optionallygenerates (1146) for presentation on the display a notification in theuser interface of the first device (e.g., cease to display the call inprogress status bar at the top of the display). For example, FIG. 10Gillustrated the first electronic device displaying a notification 1030that the second electronic device ended the phone call (e.g., “Callhang-up on Device 2 at 00:06”).

In some embodiments, the call data is optionally caused (1126) to berouted through the first electronic device to the second electronicdevice (e.g., using through-device routing, as described above). In someembodiments, causing the call data to be routed to the second electronicdevice includes sending (1128) a request to a call-routing service toroute the phone call to the second electronic device instead of routingthe phone call to the first electronic device (e.g., usingrouting-service routing, as described above).

In some embodiments, while receiving the phone call on the firstelectronic device (1102), the first electronic device plays (1114) audioassociated with the phone call at the first electronic device (e.g.,through speaker 111 illustrated in FIG. 1A). In response to detectingthe selection of the first affordance (1118), the first electronicdevice optionally ceases (1130) to play the audio associated with thephone call at the first electronic device.

In some embodiments, the first affordance is optionally included (1106)in a plurality of affordances in the user interface associated withelectronic devices capable of receiving the phone call. In someembodiments, generating the plurality of affordances optionally includes(1108) selecting the electronic devices that are associated with a useridentity of the first electronic device. In some embodiments, generatingthe plurality of affordances optionally includes (1110) selecting theelectronic devices that are connected to the same network as the firstelectronic device (e.g., the same WiFi, the same subnet, etc.). In someembodiments, generating the plurality of affordances optionally includesselecting (1112) the electronic devices that are Bluetooth discoverablefrom the first electronic device. For example, FIG. 10B illustrates aplurality of affordances 1004-1010 capable of receiving the phone call(and are optionally associated with the same user identity as the firstelectronic device, on the same network as the first electronic device,and/or Bluetooth discoverable from the first electronic device, amongother possibilities; this allows routing only to devices that arecompatible with the routing scheme and provides an element of securityto the pushing/pulling/etc.).

In some embodiments, after causing the call data associated with thephone call to be routed to the second electronic device, the firstelectronic device optionally displays (1148) an affordance for causingthe call data to be routed back to the first electronic device. Forexample, FIG. 10H illustrates the first electronic device displaying anaffordance 1032 for causing the call data to be routed back to the firstelectronic device. In some embodiments, the first electronic deviceoptionally detects (1152) selection of the affordance for causing thecall data to be routed back to the first electronic device. In responseto detecting selection of the affordance for causing the call data to berouted back to the first electronic device, the first electronic deviceoptionally causes the phone call to be routed back to the firstelectronic device. For example, FIG. 10I illustrates the phone callpresented on the second electronic device after selection of theaffordance 1032 in FIG. 10H.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described above with respect to FIGS. 1A and 3) orapplication specific chips.

The operations described above with reference to FIGS. 11A-11C are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, generating operation 1104, detecting operation 1116,instructing operation 1122, and causing operation 1124 are, optionallyimplemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

It should be understood that the particular order in which theoperations in FIGS. 11A-11C have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 900) are also applicable in an analogous manner tomethod 1100 described above with respect to FIGS. 11A-11C. For example,the user interfaces, user interface objects, affordances, phonecontrols, phone calls, routing schemes, and electronic devices describedabove with reference to method 1100 optionally have one or more of thecharacteristics of the user interfaces, user interface objects,affordances, phone controls, phone calls, routing schemes, andelectronic devices described herein with reference to other methodsdescribed herein (e.g., methods 700 and 900). For brevity, these detailsare not repeated here.

In accordance with some embodiments, FIG. 12 shows a functional blockdiagram of an electronic device 1200 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 12 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 12, an electronic device 1200 includes a display unit1202 configured to display a user interface including one or moreaffordances and/or one or more user interface objects; a communicationsunit 1204 configured to send and receive call data, phone calls,commands, instructions, etc.; an audio unit 1206 to play audio (e.g.,audio extracted from call data); optionally, an input unit 1208 toreceive user input, selections, etc. (e.g., touch-sensitive surface,keyboard, mouse, or other input unit); and a processing unit 1210coupled to the display unit 1202, the communications unit 1204, theaudio unit 1206, and the input unit 1208. In some embodiments, theprocessing unit 1210 includes a display enabling unit 1212, a receivingunit 1214, a sending unit 1216, a routing unit 1218, and an audioenabling unit 1220.

In some embodiments, the processing unit 1210 is configured to receive,at the first electronic device, a phone call (e.g., with the receivingunit 1214) that was routed to the first electronic device by acall-routing service. The processing unit 1210 is further configured to,while receiving the phone call, receive a request (e.g., with thereceiving unit 1214) to route the phone call to a second electronicdevice. The processing unit 1210 is further configured to, in responseto receiving the request to route the phone call to the secondelectronic device, and in accordance with a determination that a firstrouting criteria have been met, send a request (e.g., with the sendingunit 1216) to the call-routing service to route the phone call to thesecond electronic device instead of routing the phone call to the firstelectronic device. The processing unit 1210 is further configured to, inaccordance with a determination that a second routing criteria have beenmet, cause call data associated with the phone call to be routed throughthe first electronic device to the second electronic device (e.g., withthe routing unit 1218).

In some embodiments, the processing unit 1210 is configured to generatefor presentation on a display a user interface (e.g., with the displayenabling unit 1212) including a user interface object indicating that aphone call has been routed to a second electronic device. The processingunit 1210 is further configured to, while the user interface ispresented on the display, receive a request (e.g., with the receivingunit 1214) to route the phone call to the first electronic device. Theprocessing unit 1210 is further configured to, in response to therequest, request (e.g., with the sending unit 1216) call data associatedwith the phone call. The processing unit 1210 is further configured to,after requesting the call data, present the phone call at the firstelectronic device (e.g., with the audio enabling unit 1220).

In some embodiments, the processing unit 1210 is configured to, whilereceiving a phone call on the first electronic device: generate forpresentation on a display a user interface (e.g., with the displayenabling unit 1212) including a first affordance associated with asecond electronic device capable of receiving the phone call, and detectselection of the first affordance (e.g., with the receiving unit 1214).The processing unit 1210 is further configured to, in response todetecting the selection of the first affordance, instruct the secondelectronic device (e.g., with the sending unit 1216) to invoke a phonecall application to receive the phone call, and cause call dataassociated with the phone call to be routed to the second electronicdevice (e.g., with the routing unit 1218).

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

1. A first electronic device, comprising: one or more processors; andmemory storing one or more programs configured to be executed by the oneor more processors, the one or more programs including instructions for:receiving, at the first electronic device, a phone call that was routedto the first electronic device by a call-routing service; whilereceiving the phone call, receiving a request to route the phone call toa second electronic device; in response to receiving the request toroute the phone call to the second electronic device: in accordance witha determination that a first routing criteria have been met, sending arequest to the call-routing service to route the phone call to thesecond electronic device instead of routing the phone call to the firstelectronic device; and in accordance with a determination that a secondrouting criteria have been met, causing call data associated with thephone call to be routed through the first electronic device to thesecond electronic device.
 2. The first electronic device of claim 1,wherein: the first routing criteria include a criterion that is met whenthe call-routing service has enabled a carrier routing protocol; and thesecond routing criteria include a criterion that is met when thecall-routing service has not enabled the carrier routing protocol. 3.The first electronic device of claim 1, the one or more programs furtherincluding instructions for: before receiving the request to route thephone call, opening, at the first electronic device, a connectionassociated with the phone call; and in accordance with the determinationthat the first routing criteria have been met, closing the connectionassociated with the phone call.
 4. The first electronic device of claim3, wherein the connection associated with the phone call is closed inresponse to receiving confirmation that the second electronic device hasopened a connection associated with the phone call.
 5. The firstelectronic device of claim 3, the one or more programs further includinginstructions for: in accordance with the determination that the secondrouting criteria have been met, maintaining, on the first electronicdevice, the connection associated with the phone call for the durationof the phone call.
 6. The first electronic device of claim 5, the one ormore programs further including instructions for: receiving a hang-upcommand from the second electronic device; and in response to receivingthe hang-up command, closing the connection associated with the phonecall.
 7. The first electronic device of claim 1, wherein causing calldata associated with the phone call to be routed through the firstelectronic device to the second electronic device includes receiving thecall data and sending different data to the second electronic device. 8.The first electronic device of claim 1, wherein causing call dataassociated with the phone call to be routed through the first electronicdevice to the second electronic device includes receiving the call dataand sending the call data to the second electronic device withoutextracting audio content from the call data.
 9. The first electronicdevice of claim 1, the one or more programs further includinginstructions for: in accordance with the determination that the secondrouting criteria have been met, displaying a user interface objectindicating the phone call is routed through the first electronic device.10. The first electronic device of claim 9, the one or more programsfurther including instructions for: receiving input that corresponds toselection of the user interface object; and in response to receiving theinput, causing the call data to no longer be routed to the secondelectronic device.
 11. The first electronic device of claim 9, the oneor more programs further including instructions for: in accordance withthe determination that the first routing criteria have been met,displaying a user interface object indicating the phone call has beenrouted to the second electronic device.
 12. The first electronic deviceof claim 1, wherein the request to route the phone call to the secondelectronic device is received from the second electronic device.
 13. Thefirst electronic device of claim 1, wherein the request to route thephone call to the second electronic device corresponds to user inputreceived at the first electronic device.
 14. The first electronic deviceof claim 1, the one or more programs further including instructions for:in accordance with the determination that the second routing criteriahave been met, causing additional data to be routed to the secondelectronic device.
 15. A non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of a first electronic device, the one or more programsincluding instructions for: receiving, at the first electronic device, aphone call that was routed to the first electronic device by acall-routing service; while receiving the phone call, receiving arequest to route the phone call to a second electronic device; inresponse to receiving the request to route the phone call to the secondelectronic device: in accordance with a determination that a firstrouting criteria have been met, sending a request to the call-routingservice to route the phone call to the second electronic device insteadof routing the phone call to the first electronic device; and inaccordance with a determination that a second routing criteria have beenmet, causing call data associated with the phone call to be routedthrough the first electronic device to the second electronic device. 16.A method, comprising: at a first electronic device: receiving, at thefirst electronic device, a phone call that was routed to the firstelectronic device by a call-routing service; while receiving the phonecall, receiving a request to route the phone call to a second electronicdevice; in response to receiving the request to route the phone call tothe second electronic device: in accordance with a determination that afirst routing criteria have been met, sending a request to thecall-routing service to route the phone call to the second electronicdevice instead of routing the phone call to the first electronic device;and in accordance with a determination that a second routing criteriahave been met, causing call data associated with the phone call to berouted through the first electronic device to the second electronicdevice.